theme: load icons as Gtk does with fallback and RTL support

Forwarded: yes, https://gitlab.gnome.org/GNOME/mutter/merge_requests/62

Gbp-Pq: Name theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch

theme: use gtk_render_icon_suface to paint button icon

Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1764558
Bug-GNOME: https://gitlab.gnome.org/GNOME/mutter/issues/100
Forwarded: yes, https://gitlab.gnome.org/GNOME/mutter/merge_requests/62

This will properly take care of the icon transformations
and of the shadow.

Fixes #100

Gbp-Pq: Name theme-use-gtk_render_icon_suface-to-paint-button-icon.patch

theme, frames: Use surface device scale instead of cairo_scale

Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1764554
Bug-GNOME: https://gitlab.gnome.org/GNOME/mutter/issues/99
Forwarded: yes, https://gitlab.gnome.org/GNOME/mutter/merge_requests/61

Gtk now is caching the themed cairo surfaces, then as per
commit gtk@e36b629c the surface device scale is used to figure
out the current paint scaling.

Without this when using background-image's for window buttons
the -gtk-scaled icons isn't properly resized.

Fixes #99

Gbp-Pq: Name theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch

backends/x11: Support input-synaptics, if present.

Add support for configuring the Xorg synaptics touchpad driver.

Turns out it's very simple to support both libinput and synaptics
simultaneously, both under the heading of XI2.

Bug-Ubuntu: https://launchpad.net/bugs/1686081
Forwarded: https://gitlab.gnome.org/GNOME/mutter/merge_requests/37
Last-Update: 2018-03-16

Gbp-Pq: Name synaptics-support.patch

Skip test that started failing with 3.25

That way we can still benefit by running all the other tests.

Bug: https://bugzilla.gnome.org/785319
Applied-upstream: no

Gbp-Pq: Name skip-failing-tests-325.patch

Don't run failing tests

That way we can still benefit by running all the other tests.

Bug: https://bugzilla.gnome.org/782215
Bug: https://bugzilla.gnome.org/753836
Applied-upstream: no

Gbp-Pq: Name skip-failing-tests.patch

gtk-shell: Work around non-working startup notifications

GNOME Shell relies on the MetaScreen::startup-sequence-changed signal,
which is tied to (lib)startup-notification and therefore X11. As a result,
when we remove the startup sequence of a wayland client, GNOME Shell will
not be notified about this until startup-notification's timeout is hit.
As a temporary stop-gap, go through XWayland even for wayland clients,
so that the signal is emitted when expected.

Bug: https://bugzilla.gnome.org/show_bug.cgi?id=768531
Applied-upstream: no

Gbp-Pq: Name bgo768531_workaround-startup-notifications.patch

mutter (3.28.1-2) unstable; urgency=medium

  * Add xwayland-use-g_autoptr-for-GError-in-xserver_died.patch,
    xwayland-Don-t-abort-if-Xwayland-crashes.patch:
    - Cherry picked from upstream, to reduce noise of mutter on crashes
      which are actually caused by XWayland (LP: #1748450)

[dgit import unpatched mutter 3.28.1-2]

Import mutter_3.28.1-2.debian.tar.xz

[dgit import tarball mutter 3.28.1-2 mutter_3.28.1-2.debian.tar.xz]

Import mutter_3.28.1.orig.tar.xz

[dgit import orig mutter_3.28.1.orig.tar.xz]